Session setup control for messaging interoperability

ABSTRACT

A device includes a processor and a memory. The processor effectuates operations including receiving a service capability for a mobile originating (MO) device. The processor further effectuates operations including receiving a service capability for a mobile terminating (MT) device. The processor further effectuates operations including receiving session initiation protocol (SIP) messages from the MO device at a Breakout Gateway Control Function (BGCF). The processor further effectuates operations including determining whether the received SIP messages are associated with setting up an outgoing open group chat (OGC) or an outgoing Message Session Relay Protocol (MSRP) file transfer. The processor further effectuates operations including blocking the SIP messages in response to the determination that the SIP messages are associated with setting up a MSRP file transfer.

TECHNICAL FIELD

This disclosure is directed to multimedia communication services and,more particularly, to techniques for providing multimedia communicationservices to a subscriber.

BACKGROUND

The wireless telecommunications industry has seen tremendous growth overthe last several years. Many of today's mobile devices, such as mobilephones and personal digital assistants (PDAs), can be used asfull-service computing devices. For example, many of the most recent andadvanced mobile device can be configured to run a variety of softwareincluding productivity software (e.g., word processing, spreadsheet,presentation), communication software (e.g., email, messaging, chat,VoIP), entertainment software (e.g., games, video, audio), and variousother types of software.

This background information is provided to reveal information believedby the applicant to be of possible relevance. No admission isnecessarily intended, nor should be construed, that any of the precedinginformation constitutes prior art.

SUMMARY

The present disclosure is directed to a device having a processor and amemory coupled with the processor. The processor effectuates operationsincluding receiving a service capability for a mobile originating (MO)device. The processor further effectuates operations including receivinga service capability for a mobile terminating (MT) device. The processorfurther effectuates operations including receiving session initiationprotocol (SIP) messages from the MO device at a Breakout Gateway ControlFunction (BGCF). The processor further effectuates operations includingdetermining whether the received SIP messages are associated withsetting up an outgoing open group chat (OGC), or an outgoing MessageSession Relay Protocol (MSRP) file transfer. The processor furthereffectuates operations including routing the SIP messages to the MT inresponse to the determination that the SIP messages are associated withsetting up an outgoing OGC and establishing a rich communication service(RCS) messaging session based on the service capability of the MO deviceand the service capability of the MT device. The processor furthereffectuates operations including blocking the SIP messages in responseto the determination that the SIP messages are associated with settingup a MSRP file transfer.

The present disclosure is directed to a computer-implemented method. Thecomputer-implemented method includes receiving, by a Breakout GatewayControl Function (BGCF), a service capability for a mobile originating(MO) device. The computer-implemented method further includes receiving,by the BGCF, session initiation protocol (SIP) messages from the MOdevice. The computer-implemented method further includes receiving, bythe BGCF, session initiation protocol (SIP) messages from the MO device.The computer-implemented method further includes determining, by theBGCF, whether the received SIP messages are associated with setting upan outgoing open group chat (OGC), or an outgoing Message Session RelayProtocol (MSRP) file transfer. The computer-implemented method furtherincludes routing, by the BGCF, the SIP messages to the MT in response tothe determination that the SIP messages are associated with setting upan outgoing OGC and establishing a rich communication service (RCS)messaging session based on the service capability of the MO device andthe service capability of the MT device. The computer-implemented methodfurther includes blocking, by the BGCF, the SIP messages in response tothe determination that the SIP messages are associated with setting up aMSRP file transfer.

The present disclosure is directed to a computer-readable storage mediumstoring executable instructions that when executed by a computing devicecause said computing device to effectuate operations including receivinga service capability for a mobile originating (MO) device. Operationsfurther include receiving a service capability for a mobile terminating(MT) device. Operations further include receiving session initiationprotocol (SIP) messages from the MO device at a Breakout Gateway ControlFunction (BGCF). Operations further include determining whether thereceived SIP messages are associated with setting up an outgoing opengroup chat (OGC), or an outgoing Message Session Relay Protocol (MSRP)file transfer. Operations further include routing the SIP messages tothe MT in response to the determination that the SIP messages areassociated with setting up an outgoing OGC and establishing a richcommunication service (RCS) messaging session based on the servicecapability of the MO device and the service capability of the MT device.Operations further include blocking the SIP messages in response to thedetermination that the SIP messages are associated with setting up aMSRP file transfer.

BRIEF DESCRIPTION OF THE DRAWINGS

Aspects of the herein described telecommunications network and systemsand methods are described more fully with reference to the accompanyingdrawings, which provide examples. In the following description, forpurposes of explanation, numerous specific details are set forth inorder to provide an understanding of the variations in implementing thedisclosed technology. However, the instant disclosure may take manydifferent forms and should not be construed as limited to the examplesset forth herein. Where practical, like numbers refer to like elementsthroughout.

FIG. 1 is a block diagram of an exemplary operating environment inaccordance with the present disclosure;

FIG. 2 is a flowchart of an exemplary method of operation in accordancewith the present disclosure;

FIG. 3 is a flowchart of an exemplary method of operation in accordancewith the present disclosure;

FIG. 4 is a flowchart of an exemplary method of operation in accordancewith the present disclosure;

FIG. 5 is a schematic of an exemplary network device;

FIG. 6 depicts an exemplary communication system that provide wirelesstelecommunication services over wireless communication networks withwhich edge computing node may communicate;

FIG. 7 depicts an exemplary communication system that provide wirelesstelecommunication services over wireless communication networks withwhich edge computing node may communicate;

FIG. 8 is a diagram of an exemplary telecommunications system in whichthe disclosed methods and processes may be implemented with which edgecomputing node may communicate;

FIG. 9 is an example system diagram of a radio access network and a corenetwork with which edge computing node may communicate;

FIG. 10 depicts an overall block diagram of an example packet-basedmobile cellular network environment, such as a general packet radioservice (GPRS) network, with which edge computing node may communicate;

FIG. 11 illustrates an exemplary architecture of a GPRS network withwhich edge computing node may communicate; and

FIG. 12 is a block diagram of an exemplary public land mobile network(PLMN) with which edge computing node may communicate.

DETAILED DESCRIPTION

Modern communication devices typically have mechanisms for participatingin messaging service protocols such as text messaging by short messagingservice (SMS), multimedia messaging service (MMS) instant messaging (IM)applications, IP messaging, email, etc. These protocols are consideredpre-user profile (UP) 1.0 protocols. Because communications via thecommunication devices have become more ubiquitous, more advancedprotocols that can send and receive next generation messaging (e.g.,session-based chat, discovery presence, HTTP File Transfer, highercharacter limits, increased file size, video calls, etc.) using, forexample, Rich Communication Services (RCS) which implements UP 1.0protocols. UP 1.0 is a set of RCS standards in which the major carriersand phone manufacturers have agreed upon. Release 1.0 addressed RCS corefeatures such as capability discovery (e.g., interoperable betweenregions), chat, group chat, file transfer, audio messaging, video share,multi-device, enriched calling, location share and live sketching,enables Messaging as a Platform (MaaP), support for RCS businessmessaging, privacy control, and spam protection.

Because pre-UP 1.0 (e.g., closed group chat and MSRP file transfer) andUP 1.0 (e.g., open group chat) will be operating on the same networkuntil pre-UP 1.0 devices have been phased out, RCS messaging for UP 1.0devices coexist with pre-UP 1.0 devices and network capabilities.Accordingly, having a system that can block pre-UP 1.0 features whileallowing UP 1.0 features to establish RCS messaging sessions would bebeneficial when managing network resources.

Referring to FIG. 1, a mobile device communication architecture 100includes a telecommunications network 101, a packet core network 102,mobile devices 108 and 109, which may include display 110. The mobiledevice communication architecture 100 may also include an Internetprotocol multimedia network (IMS) 115, a messaging application server119, a presence application server 121, and partner network 150.

The telecommunications network 101 may be a 4G network or a 5G network.The packet core 102 may be for example, an Evolved Packet Core. Themobile devices 108 and 109 may be, for example, a personal computer, acomputer, or a mobile device (e.g., a laptop computer, mobiletelephones, and personal digital assistants (PDAs)). The mobile device108 may establish a session with the telecommunications network 101 viathe packet core 102 and the RAN 107 (e.g., an LTE RAN or 5G RAN). Thepartner network 150 may be a 4G network or a 5G network. The mobiledevice 109 may establish a session with the partner network 150.

The IMS network 115 may provide a framework for delivering Internetprotocol (IP) multimedia communication services (e.g., pre-UP 1.0 and UP1.0 messaging services) to wireless and wireline subscriber terminals.IMS network 115 may employ an IP-based protocol (e.g., a sessioninitiation protocol (SIP)) to facilitate integration with the Internet.The IMS network 115 may facilitate access of multimedia and voiceapplications across wireless and wireline subscriber terminals.Subscriber terminals, such as, user device 108, may register with theIMS network 115.

The IMS network 115 may include a home subscriber server (HSS) that mayimplement a subscriber database, which supports IMS network entitiesthat handle calls/sessions. The HSS typically maintainssubscription-related information (e.g., subscriber profiles), performsauthentication and authorization, and can provide information about aphysical location of a subscriber. The IMS network 115 may also includea subscriber location function (SLF) that may be used to map subscriberaddresses when multiple HSSs are used. The IMS network 115 may utilizean IP multimedia private identity (IMPI) and an IP multimedia publicidentity (IMPU). The IMPI and the IMPU are uniform resource identifiers(URIs) that may be digits (e.g., telephone URI tel: +1-512-123-4567) oralphanumeric identifiers (e.g., SIP URI sip:jane.doe@example.com). AnIMPI is unique to a subscriber terminal, which may have multiple IMPUs(e.g., a telephone URI and a SIP URI) per IMPI.

A representative set of the network entities within the IMS network 115are a call/session control function (CSCF), a media gateway controlfunction (MGCF), a media gateway (MGW). The IMS network 115 mayimplement a call/session control function, of which may include aninterrogating CSCF (I-CSCF), a proxy CSCF (P-CSCF), and a serving CSCF(S-CSCF). The P-CSCF may forward session initiation protocol (SIP)messages received from the mobile device 108 to a SIP server in a homenetwork (and vice versa). The P-CSCF may be used in conjunction with asession border controller (SBC), which protects a service provider orenterprise packet network by terminating a received call and initiatinga second call leg to a destination party. The SBC may secure a SIPnetwork and application servers and provides client/server interworkingby performing the role of a back-to-back user agent (B2BUA).

The I-CSCF may act as an entrance to a home network and providesflexibility for selecting an S-CSCF. The I-CSCF may contact a subscriberlocation function (SLF) to determine which HSS to use for a particularuser device 108. The S-CSCF may perform session control services formobile device 108, which may include routing originating sessions toexternal networks and routing terminating sessions to visited networks.The S-CSCF may also decide whether an application server (AS) receivesinformation on an incoming SIP session request to ensure appropriateservice handling and may be based on information received from the HSS.The AS may also communicate with a location server (e.g., a GatewayMobile Location Center (GMLC)) that provides a position (e.g.,latitude/longitude coordinates) for the mobile device 108.

The MGCF may provide interworking functionality between SIP sessioncontrol signaling from the IMS network 115 and call control signaling.The MGCF may also control a media gateway (MGW) that provides user-planeinterworking functionality (e.g., converting between AMR-coded andPCM-coded voice). The MGW may also communicate with other IMS networks.

The IMS network 115 may provide a variety of services for instantmessaging (IM), short messaging service (SMS), multimedia messagingservice (MMS), and rich communication services (RCS). IM is a pre-UP 1.0form of real-time communication or chatting amongst individuals usingtyped text, among other things. Messages sent to individuals who are noton-line and/or connected to the service cannot be completed.

SMS is a pre-UP 1.0 communication feature that enables short textmessaging between mobile communications devices. SMS is a hybride-mail-IM technology for mobile devices. Messages are sent and receivedutilizing a message service center that acts as an intermediary betweensenders and recipients. SMS messages are limited to text messages and inparticular short messages.

MMS is a pre-UP 1.0 extension to SMS that enables multimedia objectssuch as images and audio to be sent amongst mobile communicationdevices. MMS messages are sent in a similar fashion as SMS messagesexcept that multimedia content is first encoded and inserted in a manneranalogous to e-mail.

RCS is a UP 1.0 communication feature which utilizes a user profile foreach user device (e.g., user device 108 and user device 109). RCS allowsuser devices to send messages including high-resolution photos andlarger video files (e.g., up to 10 MB per attachment). RCS may alsoprovide an ability for a larger number of group message participants ina group chat (e.g., open group chat (OGC) or closed group chat (CGC))and sharing of files (e.g., file transfers using a Message Session RelayProtocol (1-to-1 and 1-to-N).

The messaging application server 119 may be configured to provide, forexample, instant messaging, group chat, RCS 1-1 Chat, RCS OGC, RCS CGC,or other application services. The presence application server 121 maybe in communication with the messaging application server 119 and may beconfigured to provide user presence data to the messaging applicationserver 119. The presence application server 121 may include a usercapability exchange (UCE) application server that may provide insightinto the capabilities (e.g., RCS capabilities) of user devices (e.g.,user device 108 and user device 109). For example, a resident UCE clientmay be installed on each user device 108 and user device 109 whichexchanges user capability information with the UCE application server.In addition, user devices may exchange information between each otherindicating the capabilities of each respective user device.

The presence application server 121 may be configured to receive userpresence data based on a cellular digital packet data (CDPD) presenceagent or a general packet radio service (GPRS) presence agent, orpresence data can provided by an application presence component situatedat the messaging application server 119.

RCS messaging (e.g., RCS 1-1 Chat, RCS OGC, RCS CGC, etc.) may beprovided between the user devices 108 and 109 based on user presencedata supplied by the presence application server 121. For example,initiation of an application by the user device 108 may be communicatedto the presence application server 121 as a user presence “available.”After the application is initiated, subsequent user presence data may beused to update presence server data to reflect other presenceconditions, such as, unavailable, reachable, unreachable, or others. Theapplication can be configured to provide presence updates at regular orrandom time intervals.

FIG. 2 illustrates a method of service tuple filtering during a usercapability exchange according one or more embodiments. During acommunication between a user device 108 and the presence applicationserver 121, the user device 108 may publish one or more service tuplesindicating service capabilities of the user device 108 (e.g.,Session-based Messaging (pre-UP and UP 1.0 devices, 1-to-1 RCS Chat),MSRP File Transfer (pre-UP 1.0 devices), HTTP File Transfer (UP 1.0devices), multimedia telephony (MMTel), Discovery Presence (UCE), andGeopush) to the presence application server 121, using a SIP PUBLISH.The SIP PUBLISH message may be recorded by the presence applicationserver 121. For example, the SIP PUBLISH message may entail thefollowing code:

org.3gpp.urn:urn-7:3gpp-service.ims.icsi.mmtel

org.3gpp.urn:urn-7:3gpp-application.ims.iari.rcse.dp

org.openmobilealliance:IM-session

org.openmobilealliance:IM-session (Version: 2.0)

org.openmobilealliance:ChatSession

org.openmobilealliance:ChatSession (Version: 2.0)

org.openmobilealliance:File-Transfer

org.openmobilealliance:File-Transfer (Version: 2.0)

org.3gpp.urn:urn-7:3gpp-application.ims.iari.rcs.sm

org.openmobilealliance:StandaloneMsg

org.openmobilealliance:StandaloneMsg (Version: 2.0)

org.3gpp.urn:urn-7:3gpp-application.ims.iari.rcs.fullsfgroupchat

org.openmobilealliance:File-Transfer-HTTP

org.openmobilealliance:File-Transfer-thumb

org.3gpp.urn:urn-7:3gpp-application.ims.iari.rcs.chatbot

-   -   org.3gpp.urn:urn-7:3gpp-application.ims.iari.rcs.chatbot        (Version: 2.0)

The SIP PUBLISH message code may include service tuples representingservices indicating the capabilities of the user device 108. Forexample, the services may be related to session-based messaging forpre-UP 1.0 devices, UP 1.0 devices, and 1-to-1 RCS chat), MSRP filetransfer, and HTTP file transfer.

Session setups for services of user devices may be dependent on andcontrolled by the UCE application server of the presence applicationserver 121. During a communication between the presence applicationserver 121 and the BGCF, when a mobile terminated (MT) Mobile NetworkOperator (MNO) (e.g., telecommunications network 101) provides asession-setup performed by a Mobile Originated (MO) subscriber (e.g., auser device 108), the MNO may expose respective service tuple(s) aftersending a SIP NOTIFY message to the MT by receiving a list of servicetuples from a presence application server associated with user device109. For example, the SIP NOTIFY message may indicate an occurrence ofan event and may entail the following code:

-   -   org.3gpp.urn:urn-7:3gpp-service.ims.icsi.mmtel    -   org.3gpp.urn:urn-7:3gpp-application.ims.iari.rcse.dp    -   [[org.openmobilealliance:IM-session]]    -   [[org.openmobilealliance:IM-session (Version: 2.0)]]    -   org.openmobilealliance:ChatSession    -   org.openmobilealliance:ChatSession (Version: 2.0)    -   [[org.openmobilealliance:File-Transfer]]    -   [[org.openmobilealliance:File-Transfer (Version: 2.0)]]    -   [[org.3gpp.urn:urn-7:3gpp-application.ims.iari.rcs.sm]]    -   [[org.openmobilealliance:StandaloneMsg]]    -   [[org.openmobilealliance:StandaloneMsg (Version: 2.0)]]    -   [[org.3gpp.urn:urn-7:3gpp-application.ims.iari.rcs.fullsfgroupchat]]    -   org.openmobilealliance:File-Transfer-HTTP    -   [[org.openmobilealliance:File-Transfer-thumb]]    -   [[org.3gpp.urn:urn-7:3gpp-application.ims.iari.rcs.chatbot]]    -   [[org.3gpp.urn:urn-7:3gpp-application.ims.iari.rcs.chatbot        (Version: 2.0)]]

where “[[ ]]” represents code that has been deleted or no longer valid.

As indicated in the code, lines that are stricken may represent servicetuples filtered by the presence application server associated with userdevice 109. Accordingly, the SIP NOTIFY, which is a response to a UCESIP SUBSCRIBE query, may include non-filtered service tuples.

An MO may refer to a message sent from a mobile phone (e.g., user device108). An MT may refer to a message (e.g., IM or chat) being terminatedon a mobile phone (e.g., user device 109).

During a communication between the BGCF and the SBC oftelecommunications network 101, using an interoperability of the UP 1.0,an MT MNO may provide at least one of: an RCS 1-1 chat, an RCS OGC, andan RCS HTTP file transfer, while prohibiting a Message Session RelayProtocol (MSRP) file transfer (1-1 or Group) and a CGC to user devices108 and 109. Accordingly, a MT MNO's UCE presence application servicemay expose the service tuple for session-based messaging, discoverypresence, MMTel, and HTTP file transfer, via a NOTIFY message sent to apartner carrier (e.g., an SBC of partner network 150).

During a MSRP file transfer, a MO device may establish a SIP session fora feature upon receipt of capabilities from the MT device. Performing anMSRP file transfer in this manner is problematic because security inmessaging between the MO device and MT device may not be adequatelymaintained. In order to prevent a MSRP file transfer session from beingestablished, during a communication between the SBC of thetelecommunications network 101 and the SBC of the partner network 150,the MO's presence application server (e.g., a UCE application server ofthe presence application server 121) may filter out a MSRP file transferservice tuple in an outgoing SIP NOTIFY message directed to a MT network(e.g., an SBC of the partner network 150).

The MT MNO presence application server may be used to filter servicetuples. During return communications, when an MO MNO sends a UCE SIPSUBSCRIBE message to the MT MNO presence application server, the MT MNOpresence application server may use information from the SIP SUBSCRIBEmessage to determine an identity of the MO MNO. When a match to a MT MNOhaving a UP 1.0 Interoperability Agreement occurs, the MT MNO presenceapplication server may filter service tuples received from the SIPPUBLISH, except session-based messaging, Discovery Presence, MMTel, andHTTP File Transfer. By disallowing an MSRP file transfer session or aCGC from being initiated by an MO device (e.g., user device 108),messaging may occur between user devices in a secure manner.

FIG. 3 illustrates a method of managing outgoing SIP traffic control atan IMS for traffic sent from an MO to an MT according one or moreembodiments. Outgoing control of SIP traffic may be performed at theBGCF. Accordingly, an MO (e.g., user device 108) may send SIP INVITE,SIP REFER, SIP SUBSCRIBE, and SIP MESSAGE to the messaging applicationserver 119, which forwards these communications to the BGCF.

The outgoing SIP traffic control may be utilized to conduct an RCS OGC.The RCS OGC provided herewith may include functionality related toadding or removing participants to the RCS OGC. When a user device 109is added to the RCS OGC, the user device 109 subscribes to the messagingapplication server hosting the RCS OGC to learn a status for each userdevice of the existing participants in the RCS OGC. An event associatedwith this subscription may be referred to as a conference event packagesubscription (CEPS). The CEPS may use the SIP SUBSCRIBE with an eventheader containing, for example, a “conference” tag. The BGCF may routethe SIP INVITE, SIP REFER, SIP SUBSCRIBE, and SIP MESSAGE sent by the MOto the SBC of the partner network 150. The UCE application server mayuse the SIP SUBSCRIBE to send queries in order to learn a MT'scapabilities for conducting the RCS OGC. An UCE SIP SUBSCRIBE eventheader may contain, for example, a “presence” tag. The BGCF may routeSIP messages to the MT network (e.g., telecommunications network 101 orpartner network 150).

During a messaging session setup, the Messaging Application Server 119may send OGC INVITEs to the IMS Network 115. Upon receipt of the OGCINVITEs, the BGCF may examine an Accept-contact: header. If theAccept-contact: header contains, for example,“+g.3gpp.icsi-ref=”urn%3Aurn7%3A3gppservice.ims.icsi.oma.cpm.session.group”as a value, the BGCF may allow a SIP message to proceed to the MT. Ifthe Accept-contact: header contains, for example, values indicating anon-OGC RCS Messaging sessionsetup—urn:urn-7:3gpp-service.ims.icsi.oma.cpm.filetransfer andurn:urn-7:3gpp-service.ims.icsi.oma.cpm.largemsg, the BGCF may block theSIP message.

The BGCF may manage and route outgoing SIP messages based the following:

-   -   SIP SUBSCRIBEs:        -   Allow UCE SUBSCRIBE            -   Event: presence        -   Allow Messaging Conference Event Package Subscription SIP            SUBSCRIBEs            -   Event: conference &&            -   Accept-contact:                urn:urn-7:3gpp-service.ims.icsi.oma.cpm.session.group        -   Block all other SIP SUB SCRIBES    -   SIP INVITEs:        -   Allow Messaging INVITEs            -   Accept-contact contains:            -   urn:urn-7:3gpp-service.ims.icsi.oma.cpm.session.group        -   Block non-supported Messaging INVITEs:            -   Accept-contact contains:            -   urn:urn-7:3gpp-service.ims.icsi.oma.cpm.largemsg                urn:urn-7:3gpp-service.ims.icsi.oma.cpm.filetransfer

FIG. 4 illustrates a method of managing incoming SIP traffic control atan IMS for traffic sent from an MT to an MO according one or moreembodiments. Incoming control of SIP traffic may be performed at the atthe SBC of the telecommunications 101. Accordingly, the SBC of thepartner network 150 may send SIP INVITE, SIP REFER, SIP SUBSCRIBE, andSIP MESSAGE to the SBC of the telecommunications 101, which forwardsthese communications to the user device 108.

Under UP 1.0, a CGC has not been implemented. Accordingly, thetelecommunications network 101 associated with the MO may block anyincoming session CGC requests from partner network 150 of the MT at theSBC. A CGC session setup attempt may contain, for example, “a=chatroom”portion inside a session description protocol (SDP). The SBC of thepartner network 150 may examine an SDP message body by inspecting thea=line portion of the SDP. If a=line portion contains the term“chatroom”, the SBC of the partner network 150 may block a SIP INVITE byreturning a SIP response code (e.g., a SIP 405 method not allowed). Byblocking the SIP INVITE for a CGC at the SBC of the partner network 150,establishment of a CGC session may be prevented.

While blocking CGC traffic, RCS OGC messaging traffic may be permittedto proceed to the user device 108. In RCS, an OGC session setup may beidentified as SIP INVITE's accept-contact: header containing, forexample, “urn:urn-7:3gpp-service.ims.icsi.oma.cpm.session.group” and theSBC of the telecommunications 101 may allow the messaging traffic toenter the telecommunications network 101 of the MO in response to theaccept-contact header having a session based message tag or no messagesession tag. An accept-contact header inside the SIP INVITE may contain,for example, values representing a non-OGC RCS messaging sessionsetup—urn:urn-7:3gpp-service.ims.icsi.oma.cpm.filetransfer andurn:urn-7:3gpp-service.ims.icsi.oma.cpm.largemsg are blocked by SBC fromentering the telecommunications network 101 of the MO.

When adding/removing participants in RCS messaging, an OGC may employSIP REFERs. OGC REFERs may be identified as an accept-contact: headercontaining, for example,“urn:urn-7:3gpp-service.ims.icsi.oma.cpm.session.group”. The SBC of thetelecommunications network 101 may permit OGC REFERs to proceed into thetelecommunications network 101 and blocks the SIP REFERs that do notinclude urn:urn-7:3gpp-service.ims.icsi.oma.cpm.session.group in theaccept-contact: header.

For incoming traffic, UCE SIP SUBSCRIBE messages may be permitted toenter the telecommunications network 101 of the MO in order to initiateoperation of the UCE application server. For operation of the OGC,incoming CEPS SUBSCRIBE messages may be permitted to enter thetelecommunications network 101 of the MO network. The messagingapplication server 119 may process the CEPS SUBSCRIBE messages andprovide information about current participants of OCG to newly addedparticipants of the OGC. The SBC of the telecommunications network 101may permit UCE SUBSCRIBE and CEPS SUBSCRIBE message to enter thetelecommunications network 101 while blocking other types of SIPSUBSCRIBE messages.

UCE SUBSCRIBES may be identified as SIP SUBSCRIBE when an event: headercontains, for example, “Event”. CEPS SUBSCRIBEs may be identified as SIPSUBSCRIBE when an event: header contains, for example, “Conference” as avalue and an accept-contact: header containing, for example,“urn:urn-7:3gpp-service.ims.icsi.oma.cpm.session.group”.

When an Instant Message Disposition Notification (IMDN), which may beused to store and forward status reporting and message disposition forRCS messages, is sent outside of a SIP session (e.g., for messagesession teardown), the IMDN may be sent as a SIP MESSAGE. The IMDN maybe identified by an associated message body containing a content-typeof, for example, “message/imdn+xml”. The SBC of the telecommunicationsnetwork 101 may permit IMDN MESSAGEs to proceed into thetelecommunications network 101 and blocks non-IMDN MESSAGEs.

The SBC of the telecommunications network 101 may manage and routeincoming SIP messages based the following:

SBC:

-   -   Supported Messaging SIP INVITE may be allowed by I-SBC        -   Messaging SIP INVITEs, Accept-contact header contains:            -   urn:urn-7:3gpp-service.ims.icsi.oma.cpm.session.group    -   Non-supported Messaging SIP INVITE may be rejected by I-SBC        -   Messaging SIP INVITEs, when Accept-contact header contains            the following:            -   urn:urn-7:3gpp-service.ims.icsi.oma.cpm.filetransfer            -   urn:urn-7:3gpp-service.ims.icsi.oma.cpm.largemsg        -   Messaging SIP INVITEs, when SDP contains a=chatroom.    -   SIP REFER may be allowed by I-SBC if:        -   Accept-contact: header contains urn:            urn-7:3gpp-service.ims.icsi.oma.cpm.session.group”    -   Else, reject SIP REFER    -   SIP SUBSCRIBE:        -   Allow SIP SUBSCRIBE if:            -   Contains “Event: presence” OR            -   Contains “Event: conference” if:                -   Accept-Contact: header contains                    urn:urn-7:3gpp-service.ims.icsi.oma.cpm.session.group.            -   Else, reject SIP SUBSCRIBE with “Event: conference”        -   Else reject SIP SUBSCRIBE    -   SIP MESSAGE:        -   Allow SIP MESSAGE if:            -   Content-type of “message/imdn+xml” within SDP Body                Else, reject SIP MESSAGE.

Accordingly, the present disclosure provides a system that providesSession Setup Control for Messaging Interoperability that may limit SIPsession establishment for older features of RCS Messaging (e.g., CGC)while allowing SIP session establishment for newer features of RCSMessaging (e.g., OGC). The system may allow a set of SIP messages thatan operator wants for session setup, while blocking SIP messages thatwould lead to session setup for features that the operator does notdesire (e.g. legacy messaging features). For example, by allowing UP 1.0features to establish sessions, while blocking session setups for MSRPfile transfer and CGC, the system may allow the operator to conduct aneasier transition to UP 1.0 interoperability. By blocking legacyfeatures, the system may be used to manage network resources moreefficiently by assigning resources that were once directed to the legacyfeatures to UP 1.0 features.

The system may utilize a telecommunications network that can host amessaging session and invite subscribers from a partner network to jointhe session and vice versa. Outgoing control on SIP may be done at theBGCF, while incoming control on the SIP may be at an SBC. Open GroupChat (OGC) introduces new functionalities such as “adding/removingparticipants”. Once a user device of a participant is added, the userdevice may subscribe to a messaging application server to learn a statusof each existing participant to the messaging session. An eventoccurrence of this subscription may be called a conference event packagesubscription (CEPS). CEPS may use a SIP SUBSCRIBE with event: headercontaining a “conference” tag. OGC uses SIP REFERs to add/removeparticipants.

A mobile originated (MO) can establish a SIP session to conduct an MSRPfile transfer upon receipt of user capabilities for a mobile terminated(MT). In order to prevent the MSRP file transfer session from beingestablished, a MO's presence application server may filter out a MSRPfile transfer service tuple in outgoing SIP NOTIFYs sent to a partnercarrier network.

Because a closed group chat uses the same service tuple as a 1-1 chat,other IMS network elements may be used to control session establishmentfor the closed group chat. In an instance where SIP INVITEs occur in anoutgoing direction for a closed group chat, a messaging applicationserver may be used to prevent outgoing SIP INVITEs for a closed groupchat from entering an IMS core network. In an instance where an SDPMessage body occurring in incoming direction, targeting an a=line, aSession Border Controller (SBC) may examine the a=line to determine ifthe a=line contains, for example, the term “chatroom”. Accordingly, ifthe a=line contains the term “chatroom”, the SBC may block the SIPINVITE by returning a SIP response code.

In an instance where SIP INVITEs occur in an outgoing direction for anopen group chat, the messaging application server may send SIP INVITEsto the IMS core network and upon the SIP INVITEs arriving at the bordergateway control function (BGCF), the BGCF may examine an accept-contact:header to determine if the accept-contact: header contains apredetermined value, for example,“+g.3gpp.icsi-ref=”urn%3Aurn7%3A3gppservice.ims.icsi.oma.cpm.session.group”.SIP INVITEs containing the predetermined value may represent a non-opengroup chat RCS Messaging sessionsetup—urn:urn-7:3gpp-service.ims.icsi.oma.cpm.filetransfer andurn:urn-7:3gpp-service.ims.icsi.oma.cpm.largemsg, the BGCF may block theSIP INVITEs.

In an instance where SIP SUBSCRIBEs occur, user capability exchangequeries may be allowed to proceed in order to facilitate messaginginteroperability. The user capability exchange queries may be identifiedas SIP SUBSCRIBEs when the user capability exchange has an event headercontaining a predetermined value, for example, “presence”. CEPSSUBSCRIBEs may be identified as SIP SUBSCRIBEs when the user capabilityexchange has an event header containing a predetermined value, forexample, “event”. In addition, an accept-contact header may contain“urn:urn-7:3gpp-service.ims.icsi.oma.cpm.session.group” as a value. TheBGCF may permit UCE SUBSCRIBEs and CEPS SUBSCRIBEs to proceed and blockother types of SIP SUBSCRIBEs.

In an instance where SIP REFERs occur, a BGCF may receive SIP REFERs inthe form of an open group chat “add/remove participant”. The BGCF mayreceive SIP MESSAGEs (e.g., IMDN), which may be sent outside a session.

In an instance where SIP INVITEs occur in an incoming direction for anopen group chat, the SBC may permit open group chat SIP INVITEs. The SIPINVITE's may be identified using an accept-contact header containing apredetermined value, for example,“urn:urn-7:3gpp-service.ims.icsi.oma.cpm.session.group”. If the SIPINVITEs contain values representing a non-open group chat RCS Messagingsession setup, for example,urn:urn-7:3gpp-service.ims.icsi.oma.cpm.filetransfer andurn:urn-7:3gpp-service.ims.icsi.oma.cpm.largemsg, SBC may block the SIPINVITE.

The SBC may permit UCE SUBSCRIBE and CEPS SUBSCRIBE while blocking othertypes of SIP SUBSCRIBEs. UCE SUBSCRIBEs may be identified as SIPSUBSCRIBE when the UCE SUBSCRIBE has an event header containing apredetermined value, for example, “event”. CEPS SUBSCRIBEs may beidentified as SIP SUBSCRIBE when the CEPS SUBSCRIBE has an event headercontaining a predetermined value, for example “conference”. In addition,an accept-contact: header may contain“urn:urn-7:3gpp-service.ims.icsi.oma.cpm.session.group” as value.

In an instance where SIP REFERs occur in an open group chat SIP REFERs,when adding or removing participants, the SIP REFERs may be identifiedvia an accept-contact: header containing“urn:urn-7:3gpp-service.ims.icsi.oma.cpm.session.group” value. The SBCmay permit open group chat REFERs and block other SIP REFERS.

In an instance when an IMDN is sent outside a SIP session, the IMDN maybe sent as SIP MESSAGE. The IMDN SIP message may be identified via anassociated message body containing, for example, a predeterminedcontent-type of “message/imdn+xml”. Upon identifying the IMDN SIPmessage identifying the predetermined content type, the SBC may permitthe SIP IMDN messages and blocks other SIP messages.

FIG. 5 is a block diagram of network device 300 that may be connected toor comprise a component of edge computing node or connected to edgecomputing node via a network. Network device 300 may comprise hardwareor a combination of hardware and software. The functionality tofacilitate telecommunications via a telecommunications network mayreside in one or combination of network devices 300. Network device 300depicted in FIG. 5 may represent or perform functionality of anappropriate network device 300, or combination of network devices 300,such as, for example, a component or various components of a cellularbroadcast system wireless network, a processor, a server, a gateway, anode, a mobile switching center (MSC), a short message service center(SMSC), an ALFS, a gateway mobile location center (GMLC), a radio accessnetwork (RAN), a serving mobile location center (SMLC), or the like, orany appropriate combination thereof. It is emphasized that the blockdiagram depicted in FIG. 5 is exemplary and not intended to imply alimitation to a specific implementation or configuration. Thus, networkdevice 300 may be implemented in a single device or multiple devices(e.g., single server or multiple servers, single gateway or multiplegateways, single controller, or multiple controllers). Multiple networkentities may be distributed or centrally located. Multiple networkentities may communicate wirelessly, via hard wire, or any appropriatecombination thereof.

Network device 300 may comprise a processor 302 and a memory 304 coupledto processor 302. Memory 304 may contain executable instructions that,when executed by processor 302, cause processor 302 to effectuateoperations associated with mapping wireless signal strength.

In addition to processor 302 and memory 304, network device 300 mayinclude an input/output system 306. Processor 302, memory 304, andinput/output system 306 may be coupled together (coupling not shown inFIG. 5) to allow communications therebetween. Each portion of networkdevice 300 may comprise circuitry for performing functions associatedwith each respective portion. Thus, each portion may comprise hardware,or a combination of hardware and software. Input/output system 306 maybe capable of receiving or providing information from or to acommunications device or other network entities configured fortelecommunications. For example, input/output system 306 may include awireless communications (e.g., 3G/4G/GPS) card. Input/output system 306may be capable of receiving or sending video information, audioinformation, control information, image information, data, or anycombination thereof. Input/output system 306 may be capable oftransferring information with network device 300. In variousconfigurations, input/output system 306 may receive or provideinformation via any appropriate means, such as, for example, opticalmeans (e.g., infrared), electromagnetic means (e.g., RF, Wi-Fi,Bluetooth®, ZigBee®), acoustic means (e.g., speaker, microphone,ultrasonic receiver, ultrasonic transmitter), or a combination thereof.In an example configuration, input/output system 306 may comprise aWi-Fi finder, a two-way GPS chipset or equivalent, or the like, or acombination thereof.

Input/output system 306 of network device 300 also may contain acommunication connection 308 that allows network device 300 tocommunicate with other devices, network entities, or the like.Communication connection 308 may comprise communication media.Communication media typically embody computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism and includesany information delivery media. By way of example, and not limitation,communication media may include wired media such as a wired network ordirect-wired connection, or wireless media such as acoustic, RF,infrared, or other wireless media. The term computer-readable media asused herein includes both storage media and communication media.Input/output system 306 also may include an input device 310 such askeyboard, mouse, pen, voice input device, or touch input device.Input/output system 306 may also include an output device 312, such as adisplay, speakers, or a printer.

Processor 302 may be capable of performing functions associated withtelecommunications, such as functions for processing broadcast messages,as described herein. For example, processor 302 may be capable of, inconjunction with any other portion of network device 300, determining atype of broadcast message and acting according to the broadcast messagetype or content, as described herein.

Memory 304 of network device 300 may comprise a storage medium having aconcrete, tangible, physical structure. As is known, a signal does nothave a concrete, tangible, physical structure. Memory 304, as well asany computer-readable storage medium described herein, is not to beconstrued as a signal. Memory 304, as well as any computer-readablestorage medium described herein, is not to be construed as a transientsignal. Memory 304, as well as any computer-readable storage mediumdescribed herein, is not to be construed as a propagating signal. Memory304, as well as any computer-readable storage medium described herein,is to be construed as an article of manufacture.

Memory 304 may store any information utilized in conjunction withtelecommunications. Depending upon the exact configuration or type ofprocessor, memory 304 may include a volatile storage 314 (such as sometypes of RAM), a nonvolatile storage 316 (such as ROM, flash memory), ora combination thereof. Memory 304 may include additional storage (e.g.,a removable storage 318 or a nonremovable storage 320) including, forexample, tape, flash memory, smart cards, CD-ROM, DVD, or other opticalstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, USB-compatible memory, or any othermedium that can be used to store information and that can be accessed bynetwork device 300. Memory 304 may comprise executable instructionsthat, when executed by processor 302, cause processor 302 to effectuateoperations to map signal strengths in an area of interest.

FIG. 6 illustrates a functional block diagram depicting one example ofan LTE-EPS network architecture 400 related to the current disclosure.In particular, the network architecture 400 disclosed herein is referredto as a modified LTE-EPS architecture 400 to distinguish it from atraditional LTE-EPS architecture.

An example modified LTE-EPS architecture 400 is based at least in parton standards developed by the 3rd Generation Partnership Project (3GPP),with information available at www.3gpp.org. In one embodiment, theLTE-EPS network architecture 400 includes an access network 402, a corenetwork 404, e.g., an EPC or Common BackBone (CBB) and one or moreexternal networks 406, sometimes referred to as PDN or peer entities.Different external networks 406 can be distinguished from each other bya respective network identifier, e.g., a label according to DNS namingconventions describing an access point to the PDN. Such labels can bereferred to as Access Point Names (APN). External networks 406 caninclude one or more trusted and non-trusted external networks such as aninternet protocol (IP) network 408, an IP multimedia subsystem (IMS)network 410, and other networks 412, such as a service network, acorporate network, or the like.

Access network 402 can include an LTE network architecture sometimesreferred to as Evolved Universal mobile Telecommunication systemTerrestrial Radio Access (E UTRA) and evolved UMTS Terrestrial RadioAccess Network (E-UTRAN). Broadly, access network 402 can include one ormore communication devices, commonly referred to as UE 414, and one ormore wireless access nodes, or base stations 416 a, 416 b. Duringnetwork operations, at least one base station 416 communicates directlywith UE 414. Base station 416 can be an evolved Node B (eNodeB), withwhich UE 414 communicates over the air and wirelessly. UEs 414 caninclude, without limitation, wireless devices, e.g., satellitecommunication systems, portable digital assistants (PDAs), laptopcomputers, tablet devices, Internet-of-things (IoT) devices, and othermobile devices (e.g., cellular telephones, smart appliances, and so on).UEs 414 can connect to eNBs 416 when UE 414 is within range according toa corresponding wireless communication technology.

UE 414 generally runs one or more applications that engage in a transferof packets between UE 414 and one or more external networks 406. Suchpacket transfers can include one of downlink packet transfers fromexternal network 406 to UE 414, uplink packet transfers from UE 414 toexternal network 406 or combinations of uplink and downlink packettransfers. Applications can include, without limitation, web browsing,VoIP, streaming media, and the like. Each application can pose differentQuality of Service (QoS) requirements on a respective packet transfer.Different packet transfers can be served by different bearers withincore network 404, e.g., according to parameters, such as the QoS.

Core network 404 uses a concept of bearers, e.g., EPS bearers, to routepackets, e.g., IP traffic, between a particular gateway in core network404 and UE 414. A bearer refers generally to an IP packet flow with adefined QoS between the particular gateway and UE 414. Access network402, e.g., E UTRAN, and core network 404 together set up and releasebearers as required by the various applications. Bearers can beclassified in at least two different categories: (i) minimum guaranteedbit rate bearers, e.g., for applications, such as VoIP; and (ii)non-guaranteed bit rate bearers that do not require guarantee bit rate,e.g., for applications, such as web browsing.

In one embodiment, the core network 404 includes various networkentities, such as MME 418, SGW 420, Home Subscriber Server (HSS) 422,Policy and Charging Rules Function (PCRF) 424 and PGW 426. In oneembodiment, MME 418 comprises a control node performing a controlsignaling between various equipment and devices in access network 402and core network 404. The protocols running between UE 414 and corenetwork 404 are generally known as Non-Access Stratum (NAS) protocols.

For illustration purposes only, the terms MME 418, SGW 420, HSS 422 andPGW 426, and so on, can be server devices, but may be referred to in thesubject disclosure without the word “server.” It is also understood thatany form of such servers can operate in a device, system, component, orother form of centralized or distributed hardware and software. It isfurther noted that these terms and other terms such as bearer paths orinterfaces are terms that can include features, methodologies, or fieldsthat may be described in whole or in part by standards bodies such asthe 3GPP. It is further noted that some or all embodiments of thesubject disclosure may in whole or in part modify, supplement, orotherwise supersede final or proposed standards published andpromulgated by 3GPP.

According to traditional implementations of LTE-EPS architectures, SGW420 routes and forwards all user data packets. SGW 420 also acts as amobility anchor for user plane operation during handovers between basestations, e.g., during a handover from first eNB 416 a to second eNB 416b as may be the result of UE 414 moving from one area of coverage, e.g.,cell, to another. SGW 420 can also terminate a downlink data path, e.g.,from external network 406 to UE 414 in an idle state and trigger apaging operation when downlink data arrives for UE 414. SGW 420 can alsobe configured to manage and store a context for UE 414, e.g., includingone or more of parameters of the IP bearer service and network internalrouting information. In addition, SGW 420 can perform administrativefunctions, e.g., in a visited network, such as collecting informationfor charging (e.g., the volume of data sent to or received from theuser), or replicate user traffic, e.g., to support a lawfulinterception. SGW 420 also serves as the mobility anchor forinterworking with other 3GPP technologies such as universal mobiletelecommunication system (UMTS).

At any given time, UE 414 is generally in one of three different states:detached, idle, or active. The detached state is typically a transitorystate in which UE 414 is powered on but is engaged in a process ofsearching and registering with network 402. In the active state, UE 414is registered with access network 402 and has established a wirelessconnection, e.g., radio resource control (RRC) connection, with eNB 416.Whether UE 414 is in an active state can depend on the state of a packetdata session, and whether there is an active packet data session. In theidle state, UE 414 is generally in a power conservation state in whichUE 414 typically does not communicate packets. When UE 414 is idle, SGW420 can terminate a downlink data path, e.g., from one peer entity 406,and triggers paging of UE 414 when data arrives for UE 414. If UE 414responds to the page, SGW 420 can forward the IP packet to eNB 416 a.

HSS 422 can manage subscription-related information for a user of UE414. For example, HSS 422 can store information such as authorization ofthe user, security requirements for the user, quality of service (QoS)requirements for the user, etc. HSS 422 can also hold information aboutexternal networks 406 to which the user can connect, e.g., in the formof an APN of external networks 406. For example, MME 418 can communicatewith HSS 422 to determine if UE 414 is authorized to establish a call,e.g., a voice over IP (VoIP) call before the call is established.

PCRF 424 can perform QoS management functions and policy control. PCRF424 is responsible for policy control decision-making, as well as forcontrolling the flow-based charging functionalities in a policy controlenforcement function (PCEF), which resides in PGW 426. PCRF 424 providesthe QoS authorization, e.g., QoS class identifier and bit rates thatdecide how a certain data flow will be treated in the PCEF and ensuresthat this is in accordance with the user's subscription profile.

PGW 426 can provide connectivity between the UE 414 and one or more ofthe external networks 406. In illustrative network architecture 400, PGW426 can be responsible for IP address allocation for UE 414, as well asone or more of QoS enforcement and flow-based charging, e.g., accordingto rules from the PCRF 424. PGW 426 is also typically responsible forfiltering downlink user IP packets into the different QoS-based bearers.In at least some embodiments, such filtering can be performed based ontraffic flow templates. PGW 426 can also perform QoS enforcement, e.g.,for guaranteed bit rate bearers. PGW 426 also serves as a mobilityanchor for interworking with non-3GPP technologies such as CDMA2000.

Within access network 402 and core network 404 there may be variousbearer paths/interfaces, e.g., represented by solid lines 428 and 430.Some of the bearer paths can be referred to by a specific label. Forexample, solid line 428 can be considered an S1-U bearer and solid line432 can be considered an S5/S8 bearer according to LTE-EPS architecturestandards. Without limitation, reference to various interfaces, such asS1, X2, S5, S8, S11 refer to EPS interfaces. In some instances, suchinterface designations are combined with a suffix, e.g., a “U” or a “C”to signify whether the interface relates to a “User plane” or a “Controlplane.” In addition, the core network 404 can include various signalingbearer paths/interfaces, e.g., control plane paths/interfacesrepresented by dashed lines 430, 434, 436, and 438. Some of thesignaling bearer paths may be referred to by a specific label. Forexample, dashed line 430 can be considered as an S1-MME signalingbearer, dashed line 434 can be considered as an S11 signaling bearer anddashed line 436 can be considered as an S6a signaling bearer, e.g.,according to LTE-EPS architecture standards. The above bearer paths andsignaling bearer paths are only illustrated as examples and it should benoted that additional bearer paths and signaling bearer paths may existthat are not illustrated.

Also shown is a novel user plane path/interface, referred to as theS1-U+ interface 466. In the illustrative example, the S1-U+ user planeinterface extends between the eNB 416 a and PGW 426. Notably, S1-U+path/interface does not include SGW 420, a node that is otherwiseinstrumental in configuring or managing packet forwarding between eNB416 a and one or more external networks 406 by way of PGW 426. Asdisclosed herein, the S1-U+ path/interface facilitates autonomouslearning of peer transport layer addresses by one or more of the networknodes to facilitate a self-configuring of the packet forwarding path. Inparticular, such self-configuring can be accomplished during handoversin most scenarios so as to reduce any extra signaling load on the S/PGWs420, 426 due to excessive handover events.

In some embodiments, PGW 426 is coupled to storage device 440, shown inphantom. Storage device 440 can be integral to one of the network nodes,such as PGW 426, for example, in the form of internal memory or diskdrive. It is understood that storage device 440 can include registerssuitable for storing address values. Alternatively or in addition,storage device 440 can be separate from PGW 426, for example, as anexternal hard drive, a flash drive, or network storage.

Storage device 440 selectively stores one or more values relevant to theforwarding of packet data. For example, storage device 440 can storeidentities or addresses of network entities, such as any of networknodes 418, 420, 422, 424, and 426, eNBs 416 or UE 414. In theillustrative example, storage device 440 includes a first storagelocation 442 and a second storage location 444. First storage location442 can be dedicated to storing a Currently Used Downlink address value442. Likewise, second storage location 444 can be dedicated to storing aDefault Downlink Forwarding address value 444. PGW 426 can read or writevalues into either of storage locations 442, 444, for example, managingCurrently Used Downlink Forwarding address value 442 and DefaultDownlink Forwarding address value 444 as disclosed herein.

In some embodiments, the Default Downlink Forwarding address for eachEPS bearer is the SGW S5-U address for each EPS Bearer. The CurrentlyUsed Downlink Forwarding address” for each EPS bearer in PGW 426 can beset every time when PGW 426 receives an uplink packet, e.g., a GTP-Uuplink packet, with a new source address for a corresponding EPS bearer.When UE 414 is in an idle state, the “Current Used Downlink Forwardingaddress” field for each EPS bearer of UE 414 can be set to a “null” orother suitable value.

In some embodiments, the Default Downlink Forwarding address is onlyupdated when PGW 426 receives a new SGW S5-U address in a predeterminedmessage or messages. For example, the Default Downlink Forwardingaddress is only updated when PGW 426 receives one of a Create SessionRequest, Modify Bearer Request and Create Bearer Response messages fromSGW 420.

As values 442, 444 can be maintained and otherwise manipulated on a perbearer basis, it is understood that the storage locations can take theform of tables, spreadsheets, lists, or other data structures generallywell understood and suitable for maintaining or otherwise manipulateforwarding addresses on a per bearer basis.

It should be noted that access network 402 and core network 404 areillustrated in a simplified block diagram in FIG. 6. In other words,either or both of access network 402 and the core network 404 caninclude additional network elements that are not shown, such as variousrouters, switches, and controllers. In addition, although FIG. 6illustrates only a single one of each of the various network elements,it should be noted that access network 402 and core network 404 caninclude any number of the various network elements. For example, corenetwork 404 can include a pool (i.e., more than one) of MMEs 418, SGWs420 or PGWs 426.

In the illustrative example, data traversing a network path between UE414, eNB 416 a, SGW 420, PGW 426 and external network 406 may beconsidered to constitute data transferred according to an end-to-end IPservice. However, for the present disclosure, to properly performestablishment management in LTE-EPS network architecture 400, the corenetwork, data bearer portion of the end-to-end IP service is analyzed.

An establishment may be defined herein as a connection set up requestbetween any two elements within LTE-EPS network architecture 400. Theconnection set up request may be for user data or for signaling. Afailed establishment may be defined as a connection set up request thatwas unsuccessful. A successful establishment may be defined as aconnection set up request that was successful.

In one embodiment, a data bearer portion comprises a first portion(e.g., a data radio bearer 446) between UE 414 and eNB 416 a, a secondportion (e.g., an S1 data bearer 428) between eNB 416 a and SGW 420, anda third portion (e.g., an S5/S8 bearer 432) between SGW 420 and PGW 426.Various signaling bearer portions are also illustrated in FIG. 6. Forexample, a first signaling portion (e.g., a signaling radio bearer 448)between UE 414 and eNB 416 a, and a second signaling portion (e.g., S1signaling bearer 430) between eNB 416 a and MME 418.

In at least some embodiments, the data bearer can include tunneling,e.g., IP tunneling, by which data packets can be forwarded in anencapsulated manner, between tunnel endpoints. Tunnels, or tunnelconnections can be identified in one or more nodes of network 400, e.g.,by one or more of tunnel endpoint identifiers, an IP address, and a userdatagram protocol port number. Within a particular tunnel connection,payloads, e.g., packet data, which may or may not include protocolrelated information, are forwarded between tunnel endpoints.

An example of first tunnel solution 450 includes a first tunnel 452 abetween two tunnel endpoints 454 a and 456 a, and a second tunnel 452 bbetween two tunnel endpoints 454 b and 456 b. In the illustrativeexample, first tunnel 452 a is established between eNB 416 a and SGW420. Accordingly, first tunnel 452 a includes a first tunnel endpoint454 a corresponding to an S1-U address of eNB 416 a (referred to hereinas the eNB S1-U address), and second tunnel endpoint 456 a correspondingto an S1-U address of SGW 420 (referred to herein as the SGW S1-Uaddress). Likewise, second tunnel 452 b includes first tunnel endpoint454 b corresponding to an S5-U address of SGW 420 (referred to herein asthe SGW S5-U address), and second tunnel endpoint 456 b corresponding toan S5-U address of PGW 426 (referred to herein as the PGW S5-U address).

In at least some embodiments, first tunnel solution 450 is referred toas a two-tunnel solution, e.g., according to the GPRS Tunneling ProtocolUser Plane (GTPv1-U based), as described in 3GPP specification TS29.281, incorporated herein in its entirety. It is understood that oneor more tunnels are permitted between each set of tunnel end points. Forexample, each subscriber can have one or more tunnels, e.g., one foreach PDP context that they have active, as well as possibly havingseparate tunnels for specific connections with different quality ofservice requirements, and so on.

An example of second tunnel solution 458 includes a single or directtunnel 460 between tunnel endpoints 462 and 464. In the illustrativeexample, direct tunnel 460 is established between eNB 416 a and PGW 426,without subjecting packet transfers to processing related to SGW 420.Accordingly, direct tunnel 460 includes first tunnel endpoint 462corresponding to the eNB S1-U address, and second tunnel endpoint 464corresponding to the PGW S5-U address. Packet data received at eitherend can be encapsulated into a payload and directed to the correspondingaddress of the other end of the tunnel. Such direct tunneling avoidsprocessing, e.g., by SGW 420 that would otherwise relay packets betweenthe same two endpoints, e.g., according to a protocol, such as the GTP-Uprotocol.

In some scenarios, direct tunneling solution 458 can forward user planedata packets between eNB 416 a and PGW 426, by way of SGW 420. Forexample, SGW 420 can serve a relay function, by relaying packets betweentwo tunnel endpoints 416 a, 426. In other scenarios, direct tunnelingsolution 458 can forward user data packets between eNB 416 a and PGW426, by way of the S1 U+ interface, thereby bypassing SGW 420.

Generally, UE 414 can have one or more bearers at any one time. Thenumber and types of bearers can depend on applications, defaultrequirements, and so on. It is understood that the techniques disclosedherein, including the configuration, management and use of varioustunnel solutions 450, 458, can be applied to the bearers on anindividual basis. For example, if user data packets of one bearer, say abearer associated with a VoIP service of UE 414, then the forwarding ofall packets of that bearer are handled in a similar manner. Continuingwith this example, the same UE 414 can have another bearer associatedwith it through the same eNB 416 a. This other bearer, for example, canbe associated with a relatively low rate data session forwarding userdata packets through core network 404 simultaneously with the firstbearer. Likewise, the user data packets of the other bearer are alsohandled in a similar manner, without necessarily following a forwardingpath or solution of the first bearer. Thus, one of the bearers may beforwarded through direct tunnel 458; whereas, another one of the bearersmay be forwarded through a two-tunnel solution 450.

FIG. 7 depicts an exemplary diagrammatic representation of a machine inthe form of a computer system 500 within which a set of instructions,when executed, may cause the machine to perform any one or more of themethods described above. One or more instances of the machine canoperate, for example, as processor 302, UE 414, eNB 416, MME 418, SGW420, HSS 422, PCRF 424, PGW 426 and other devices of FIG. 6. In someembodiments, the machine may be connected (e.g., using a network 502) toother machines. In a networked deployment, the machine may operate inthe capacity of a server or a client user machine in a server-clientuser network environment, or as a peer machine in a peer-to-peer (ordistributed) network environment.

The machine may comprise a server computer, a client user computer, apersonal computer (PC), a tablet, a smart phone, a laptop computer, adesktop computer, a control system, a network router, switch or bridge,or any machine capable of executing a set of instructions (sequential orotherwise) that specify actions to be taken by that machine. It will beunderstood that a communication device of the subject disclosureincludes broadly any electronic device that provides voice, video, ordata communication. Further, while a single machine is illustrated, theterm “machine” shall also be taken to include any collection of machinesthat individually or jointly execute a set (or multiple sets) ofinstructions to perform any one or more of the methods discussed herein.

Computer system 500 may include a processor (or controller) 504 (e.g., acentral processing unit (CPU)), a graphics processing unit (GPU, orboth), a main memory 506 and a static memory 508, which communicate witheach other via a bus 510. The computer system 500 may further include adisplay unit 512 (e.g., a liquid crystal display (LCD), a flat panel, ora solid-state display). Computer system 500 may include an input device514 (e.g., a keyboard), a cursor control device 516 (e.g., a mouse), adisk drive unit 518, a signal generation device 520 (e.g., a speaker orremote control) and a network interface device 522. In distributedenvironments, the embodiments described in the subject disclosure can beadapted to utilize multiple display units 512 controlled by two or morecomputer systems 500. In this configuration, presentations described bythe subject disclosure may in part be shown in a first of display units512, while the remaining portion is presented in a second of displayunits 512.

The disk drive unit 518 may include a tangible computer-readable storagemedium 524 on which is stored one or more sets of instructions (e.g.,software 526) embodying any one or more of the methods or functionsdescribed herein, including those methods illustrated above.Instructions 526 may also reside, completely or at least partially,within main memory 506, static memory 508, or within processor 504during execution thereof by the computer system 500. Main memory 506 andprocessor 504 also may constitute tangible computer-readable storagemedia.

As shown in FIG. 8, telecommunication system 600 may include wirelesstransmit/receive units (WTRUs) 602, a RAN 604, a core network 606, apublic switched telephone network (PSTN) 608, the Internet 610, or othernetworks 612, though it will be appreciated that the disclosed examplescontemplate any number of WTRUs, base stations, networks, or networkelements. Each WTRU 602 may be any type of device configured to operateor communicate in a wireless environment. For example, a WTRU maycomprise IoT devices 32, mobile devices 33, network device 300, or thelike, or any combination thereof. By way of example, WTRUs 602 may beconfigured to transmit or receive wireless signals and may include a UE,a mobile station, a mobile device, a fixed or mobile subscriber unit, apager, a cellular telephone, a PDA, a smartphone, a laptop, a netbook, apersonal computer, a wireless sensor, consumer electronics, or the like.WTRUs 602 may be configured to transmit or receive wireless signals overan air interface 614.

Telecommunication system 600 may also include one or more base stations616. Each of base stations 616 may be any type of device configured towirelessly interface with at least one of the WTRUs 602 to facilitateaccess to one or more communication networks, such as core network 606,PTSN 608, Internet 610, or other networks 612. By way of example, basestations 616 may be a base transceiver station (BTS), a Node-B, aneNodeB, a Home Node B, a Home eNodeB, a site controller, an access point(AP), a wireless router, or the like. While base stations 616 are eachdepicted as a single element, it will be appreciated that base stations616 may include any number of interconnected base stations or networkelements.

RAN 604 may include one or more base stations 616, along with othernetwork elements (not shown), such as a base station controller (BSC), aradio network controller (RNC), or relay nodes. One or more basestations 616 may be configured to transmit or receive wireless signalswithin a particular geographic region, which may be referred to as acell (not shown). The cell may further be divided into cell sectors. Forexample, the cell associated with base station 616 may be divided intothree sectors such that base station 616 may include three transceivers:one for each sector of the cell. In another example, base station 616may employ multiple-input multiple-output (MIMO) technology and,therefore, may utilize multiple transceivers for each sector of thecell.

Base stations 616 may communicate with one or more of WTRUs 602 over airinterface 614, which may be any suitable wireless communication link(e.g., RF, microwave, infrared (IR), ultraviolet (UV), or visiblelight). Air interface 614 may be established using any suitable radioaccess technology (RAT).

More specifically, as noted above, telecommunication system 600 may be amultiple access system and may employ one or more channel accessschemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, or the like. Forexample, base station 616 in RAN 604 and WTRUs 602 connected to RAN 604may implement a radio technology such as Universal MobileTelecommunications System (UMTS) Terrestrial Radio Access (UTRA) thatmay establish air interface 614 using wideband CDMA (WCDMA). WCDMA mayinclude communication protocols, such as High-Speed Packet Access (HSPA)or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink PacketAccess (HSDPA) or High-Speed Uplink Packet Access (HSUPA).

As another example base station 616 and WTRUs 602 that are connected toRAN 604 may implement a radio technology such as Evolved UMTSTerrestrial Radio Access (E-UTRA), which may establish air interface 614using LTE or LTE-Advanced (LTE-A).

Optionally base station 616 and WTRUs 602 connected to RAN 604 mayimplement radio technologies such as IEEE 602.16 (i.e., WorldwideInteroperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1×,CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95(IS-95), Interim Standard 856 (IS-856), GSM, Enhanced Data rates for GSMEvolution (EDGE), GSM EDGE (GERAN), or the like.

Base station 616 may be a wireless router, Home Node B, Home eNodeB, oraccess point, for example, and may utilize any suitable RAT forfacilitating wireless connectivity in a localized area, such as a placeof business, a home, a vehicle, a campus, or the like. For example, basestation 616 and associated WTRUs 602 may implement a radio technologysuch as IEEE 602.11 to establish a wireless local area network (WLAN).As another example, base station 616 and associated WTRUs 602 mayimplement a radio technology such as IEEE 602.15 to establish a wirelesspersonal area network (WPAN). In yet another example, base station 616and associated WTRUs 602 may utilize a cellular-based RAT (e.g., WCDMA,CDMA2000, GSM, LTE, LTE-A, etc.) to establish a picocell or femtocell.As shown in FIG. 8, base station 616 may have a direct connection toInternet 610. Thus, base station 616 may not be required to accessInternet 610 via core network 606.

RAN 604 may be in communication with core network 606, which may be anytype of network configured to provide voice, data, applications, orvoice over internet protocol (VoIP) services to one or more WTRUs 602.For example, core network 606 may provide call control, billingservices, mobile location-based services, pre-paid calling, Internetconnectivity, video distribution or high-level security functions, suchas user authentication. Although not shown in FIG. 8, it will beappreciated that RAN 604 or core network 606 may be in direct orindirect communication with other RANs that employ the same RAT as RAN604 or a different RAT. For example, in addition to being connected toRAN 604, which may be utilizing an E-UTRA radio technology, core network606 may also be in communication with another RAN (not shown) employinga GSM radio technology.

Core network 606 may also serve as a gateway for WTRUs 602 to accessPSTN 608, Internet 610, or other networks 612. PSTN 608 may includecircuit-switched telephone networks that provide plain old telephoneservice (POTS). For LTE core networks, core network 606 may use IMS core614 to provide access to PSTN 608. Internet 610 may include a globalsystem of interconnected computer networks or devices that use commoncommunication protocols, such as the transmission control protocol(TCP), user datagram protocol (UDP), or IP in the TCP/IP internetprotocol suite. Other networks 612 may include wired or wirelesscommunications networks owned or operated by other service providers.For example, other networks 612 may include another core networkconnected to one or more RANs, which may employ the same RAT as RAN 604or a different RAT.

Some or all WTRUs 602 in telecommunication system 600 may includemulti-mode capabilities. For example, WTRUs 602 may include multipletransceivers for communicating with different wireless networks overdifferent wireless links. For example, one or more WTRUs 602 may beconfigured to communicate with base station 616, which may employ acellular-based radio technology, and with base station 616, which mayemploy an IEEE 802 radio technology.

FIG. 9 is an example system 700 including RAN 604 and core network 606.As noted above, RAN 604 may employ an E-UTRA radio technology tocommunicate with WTRUs 602 over air interface 614. RAN 604 may also bein communication with core network 606.

RAN 604 may include any number of eNodeBs 702 while remaining consistentwith the disclosed technology. One or more eNodeBs 702 may include oneor more transceivers for communicating with the WTRUs 602 over airinterface 614. Optionally, eNodeBs 702 may implement MIMO technology.Thus, one of eNodeBs 702, for example, may use multiple antennas totransmit wireless signals to, or receive wireless signals from, one ofWTRUs 602.

Each of eNodeBs 702 may be associated with a particular cell (not shown)and may be configured to handle radio resource management decisions,handover decisions, scheduling of users in the uplink or downlink, orthe like. As shown in FIG. 9 eNodeBs 702 may communicate with oneanother over an X2 interface.

Core network 606 shown in FIG. 9 may include a mobility managementgateway or entity (MME) 704, a serving gateway 706, or a packet datanetwork (PDN) gateway 708. While each of the foregoing elements aredepicted as part of core network 606, it will be appreciated that anyone of these elements may be owned or operated by an entity other thanthe core network operator.

MME 704 may be connected to each of eNodeBs 702 in RAN 604 via an S1interface and may serve as a control node. For example, MME 704 may beresponsible for authenticating users of WTRUs 602, bearer activation ordeactivation, selecting a particular serving gateway during an initialattach of WTRUs 602, or the like. MME 704 may also provide a controlplane function for switching between RAN 604 and other RANs (not shown)that employ other radio technologies, such as GSM or WCDMA.

Serving gateway 706 may be connected to each of eNodeBs 702 in RAN 604via the S1 interface. Serving gateway 706 may generally route or forwarduser data packets to or from the WTRUs 602. Serving gateway 706 may alsoperform other functions, such as anchoring user planes duringinter-eNodeB handovers, triggering paging when downlink data isavailable for WTRUs 602, managing or storing contexts of WTRUs 602, orthe like.

Serving gateway 706 may also be connected to PDN gateway 708, which mayprovide WTRUs 602 with access to packet-switched networks, such asInternet 610, to facilitate communications between WTRUs 602 andIP-enabled devices.

Core network 606 may facilitate communications with other networks. Forexample, core network 606 may provide WTRUs 602 with access tocircuit-switched networks, such as PSTN 608, such as through IMS core614, to facilitate communications between WTRUs 602 and traditionalland-line communications devices. In addition, core network 606 mayprovide the WTRUs 602 with access to other networks 612, which mayinclude other wired or wireless networks that are owned or operated byother service providers.

FIG. 10 depicts an overall block diagram of an example packet-basedmobile cellular network environment, such as a GPRS network as describedherein. In the example packet-based mobile cellular network environmentshown in FIG. 10, there are a plurality of base station subsystems (BSS)800 (only one is shown), each of which comprises a base stationcontroller (BSC) 802 serving a plurality of BTSs, such as BTSs 804, 806,808. BTSs 804, 806, 808 are the access points where users ofpacket-based mobile devices become connected to the wireless network. Inexample fashion, the packet traffic originating from mobile devices istransported via an over-the-air interface to BTS 808, and from BTS 808to BSC 802. Base station subsystems, such as BSS 800, are a part ofinternal frame relay network 810 that can include a service GPRS supportnodes (SGSN), such as SGSN 812 or SGSN 814. Each SGSN 812, 814 isconnected to an internal packet network 816 through which SGSN 812, 814can route data packets to or from a plurality of gateway GPRS supportnodes (GGSN) 818, 820, 822. As illustrated, SGSN 814 and GGSNs 818, 820,822 are part of internal packet network 816. GGSNs 818, 820, 822 mainlyprovide an interface to external IP networks such as PLMN 824, corporateintranets/internets 826, or Fixed-End System (FES) or the publicInternet 828. As illustrated, subscriber corporate network 826 may beconnected to GGSN 820 via a firewall 830. PLMN 824 may be connected toGGSN 820 via a boarder gateway router (BGR) 832. A Remote AuthenticationDial-In User Service (RADIUS) server 834 may be used for callerauthentication when a user calls corporate network 826.

Generally, there may be a several cell sizes in a network, referred toas macro, micro, pico, femto or umbrella cells. The coverage area ofeach cell is different in different environments. Macro cells can beregarded as cells in which the base station antenna is installed in amast or a building above average roof top level. Micro cells are cellswhose antenna height is under average roof top level. Micro cells aretypically used in urban areas. Pico cells are small cells having adiameter of a few dozen meters. Pico cells are used mainly indoors.Femto cells have the same size as pico cells, but a smaller transportcapacity. Femto cells are used indoors, in residential or small businessenvironments. On the other hand, umbrella cells are used to covershadowed regions of smaller cells and fill in gaps in coverage betweenthose cells.

FIG. 11 illustrates an architecture of a typical GPRS network 900 asdescribed herein. The architecture depicted in FIG. 11 may be segmentedinto four groups: users 902, RAN 904, core network 906, and interconnectnetwork 908. Users 902 comprise a plurality of end users, who each mayuse one or more devices 910. Note that device 910 is referred to as amobile subscriber (MS) in the description of network shown in FIG. 11.In an example, device 910 comprises a communications device (e.g., IoTdevices 32, mobile positioning center 116, network device 300, any ofdetected devices 500, second device 508, access device 604, accessdevice 606, access device 608, access device 610 or the like, or anycombination thereof). Radio access network 904 comprises a plurality ofBSSs such as BSS 912, which includes a BTS 914 and a BSC 916. Corenetwork 906 may include a host of various network elements. Asillustrated in FIG. 11, core network 906 may comprise MSC 918, servicecontrol point (SCP) 920, gateway MSC (GMSC) 922, SGSN 924, home locationregister (HLR) 926, authentication center (AuC) 928, domain name system(DNS) server 930, and GGSN 932. Interconnect network 908 may alsocomprise a host of various networks or other network elements. Asillustrated in FIG. 11, interconnect network 908 comprises a PSTN 934, aFES/Internet 936, a firewall 1038, or a corporate network 940.

An MSC can be connected to a large number of BSCs. At MSC 918, forinstance, depending on the type of traffic, the traffic may be separatedin that voice may be sent to PSTN 934 through GMSC 922, or data may besent to SGSN 924, which then sends the data traffic to GGSN 932 forfurther forwarding.

When MSC 918 receives call traffic, for example, from BSC 916, it sendsa query to a database hosted by SCP 920, which processes the request andissues a response to MSC 918 so that it may continue call processing asappropriate.

HLR 926 is a centralized database for users to register to the GPRSnetwork. HLR 926 stores static information about the subscribers such asthe International Mobile Subscriber Identity (IMSI), subscribedservices, or a key for authenticating the subscriber. HLR 926 alsostores dynamic subscriber information such as the current location ofthe MS. Associated with HLR 926 is AuC 928, which is a database thatcontains the algorithms for authenticating subscribers and includes theassociated keys for encryption to safeguard the user input forauthentication.

In the following, depending on context, “mobile subscriber” or “MS”sometimes refers to the end user and sometimes to the actual portabledevice, such as a mobile device, used by an end user of the mobilecellular service. When a mobile subscriber turns on his or her mobiledevice, the mobile device goes through an attach process by which themobile device attaches to an SGSN of the GPRS network. In FIG. 11, whenMS 910 initiates the attach process by turning on the networkcapabilities of the mobile device, an attach request is sent by MS 910to SGSN 924. The SGSN 924 queries another SGSN, to which MS 910 wasattached before, for the identity of MS 910. Upon receiving the identityof MS 910 from the other SGSN, SGSN 924 requests more information fromMS 910. This information is used to authenticate MS 910 together withthe information provided by HLR 926. Once verified, SGSN 924 sends alocation update to HLR 926 indicating the change of location to a newSGSN, in this case SGSN 924. HLR 926 notifies the old SGSN, to which MS910 was attached before, to cancel the location process for MS 910. HLR926 then notifies SGSN 924 that the location update has been performed.At this time, SGSN 924 sends an Attach Accept message to MS 910, whichin turn sends an Attach Complete message to SGSN 924.

Next, MS 910 establishes a user session with the destination network,corporate network 940, by going through a Packet Data Protocol (PDP)activation process. Briefly, in the process, MS 910 requests access tothe Access Point Name (APN), for example, UPS.com, and SGSN 924 receivesthe activation request from MS 910. SGSN 924 then initiates a DNS queryto learn which GGSN 932 has access to the UPS.com APN. The DNS query issent to a DNS server within core network 906, such as DNS server 930,which is provisioned to map to one or more GGSNs in core network 906.Based on the APN, the mapped GGSN 932 can access requested corporatenetwork 940. SGSN 924 then sends to GGSN 932 a Create PDP ContextRequest message that contains necessary information. GGSN 932 sends aCreate PDP Context Response message to SGSN 924, which then sends anActivate PDP Context Accept message to MS 910.

Once activated, data packets of the call made by MS 910 can then gothrough RAN 904, core network 906, and interconnect network 908, in aparticular FES/Internet 936 and firewall 1038, to reach corporatenetwork 940.

FIG. 12 illustrates a PLMN block diagram view of an example architecturethat may be replaced by a telecommunications system. In FIG. 12, solidlines may represent user traffic signals, and dashed lines may representsupport signaling. MS 1002 is the physical equipment used by the PLMNsubscriber. For example, IoT devices 32, network device 300, the like,or any combination thereof may serve as MS 1002. MS 1002 may be one of,but not limited to, a cellular telephone, a cellular telephone incombination with another electronic device or any other wireless mobilecommunication device.

MS 1002 may communicate wirelessly with BSS 1004. BSS 1004 contains BSC1006 and a BTS 1008. BSS 1004 may include a single BSC 1006/BTS 1008pair (base station) or a system of BSC/BTS pairs that are part of alarger network. BSS 1004 is responsible for communicating with MS 1002and may support one or more cells. BSS 1004 is responsible for handlingcellular traffic and signaling between MS 1002 and a core network 1010.Typically, BSS 1004 performs functions that include, but are not limitedto, digital conversion of speech channels, allocation of channels tomobile devices, paging, or transmission/reception of cellular signals.

Additionally, MS 1002 may communicate wirelessly with RNS 1012. RNS 1012contains a Radio Network Controller (RNC) 1014 and one or more Nodes B1016. RNS 1012 may support one or more cells. RNS 1012 may also includeone or more RNC 1014/Node B 1016 pairs or alternatively a single RNC1014 may manage multiple Nodes B 1016. RNS 1012 is responsible forcommunicating with MS 1002 in its geographically defined area. RNC 1014is responsible for controlling Nodes B 1016 that are connected to it andis a control element in a UMTS radio access network. RNC 1014 performsfunctions such as, but not limited to, load control, packet scheduling,handover control, security functions, or controlling MS 1002 access tocore network 1010.

An E-UTRA Network (E-UTRAN) 1018 is a RAN that provides wireless datacommunications for MS 1002 and UE 1024. E-UTRAN 1018 provides higherdata rates than traditional UMTS. It is part of the LTE upgrade formobile networks, and later releases meet the requirements of theInternational Mobile Telecommunications (IMT) Advanced and are commonlyknown as a 4G networks. E-UTRAN 1018 may include of series of logicalnetwork components such as E-UTRAN Node B (eNB) 1020 and E-UTRAN Node B(eNB) 1022. E-UTRAN 1018 may contain one or more eNBs. User equipment(UE) 1024 may be any mobile device capable of connecting to E-UTRAN 1018including, but not limited to, a personal computer, laptop, mobiledevice, wireless router, or other device capable of wirelessconnectivity to E-UTRAN 1018. The improved performance of the E-UTRAN1018 relative to a typical UMTS network allows for increased bandwidth,spectral efficiency, and functionality including, but not limited to,voice, high-speed applications, large data transfer or IPTV, while stillallowing for full mobility.

Typically, MS 1002 may communicate with any or all of BSS 1004, RNS1012, or E-UTRAN 1018. In an illustrative system, each of BSS 1004, RNS1012, and E-UTRAN 1018 may provide MS 1002 with access to core network1010. Core network 1010 may include of a series of devices that routedata and communications between end users. Core network 1010 may providenetwork service functions to users in the circuit switched (CS) domainor the packet switched (PS) domain. The CS domain refers to connectionsin which dedicated network resources are allocated at the time ofconnection establishment and then released when the connection isterminated. The PS domain refers to communications and data transfersthat make use of autonomous groupings of bits called packets. Eachpacket may be routed, manipulated, processed, or handled independentlyof all other packets in the PS domain and does not require dedicatednetwork resources.

The circuit-switched MGW function (CS-MGW) 1026 is part of core network1010 and interacts with VLR/MSC server 1028 and GMSC server 1030 inorder to facilitate core network 1010 resource control in the CS domain.Functions of CS-MGW 1026 include, but are not limited to, mediaconversion, bearer control, payload processing or other mobile networkprocessing such as handover or anchoring. CS-MGW 1026 may receiveconnections to MS 1002 through BSS 1004 or RNS 1012.

SGSN 1032 stores subscriber data regarding MS 1002 in order tofacilitate network functionality. SGSN 1032 may store subscriptioninformation such as, but not limited to, the IMSI, temporary identities,or PDP addresses. SGSN 1032 may also store location information such as,but not limited to, GGSN address for each GGSN 1034 where an active PDPexists. GGSN 1034 may implement a location register function to storesubscriber data it receives from SGSN 1032 such as subscription orlocation information.

Serving gateway (S-GW) 1036 is an interface which provides connectivitybetween E-UTRAN 1018 and core network 1010. Functions of S-GW 1036include, but are not limited to, packet routing, packet forwarding,transport level packet processing, or user plane mobility anchoring forinter-network mobility. PCRF 1038 uses information gathered from PGW1036, as well as other sources, to make applicable policy and chargingdecisions related to data flows, network resources or other networkadministration functions. PDN gateway (PDN-GW) 1040 may provideuser-to-services connectivity functionality including, but not limitedto, GPRS/EPC network anchoring, bearer session anchoring and control, orIP address allocation for PS domain connections.

HSS 1042 is a database for user information and stores subscription dataregarding MS 1002 or UE 1024 for handling calls or data sessions.Networks may contain one HSS 1042 or more if additional resources arerequired. Example data stored by HSS 1042 include, but is not limitedto, user identification, numbering or addressing information, securityinformation, or location information. HSS 1042 may also provide call orsession establishment procedures in both the PS and CS domains.

VLR/MSC Server 1028 provides user location functionality. When MS 1002enters a new network location, it begins a registration procedure. AnMSC server for that location transfers the location information to theVLR for the area. A VLR and MSC server may be located in the samecomputing environment, as is shown by VLR/MSC server 1028, oralternatively may be located in separate computing environments. A VLRmay contain, but is not limited to, user information such as the IMSI,the Temporary Mobile Station Identity (TMSI), the Local Mobile StationIdentity (LMSI), the last known location of the mobile station, or theSGSN where the mobile station was previously registered. The MSC servermay contain information such as, but not limited to, procedures for MS1002 registration or procedures for handover of MS 1002 to a differentsection of core network 1010. GMSC server 1030 may serve as a connectionto alternate GMSC servers for other MSs in larger networks.

EIR 1044 is a logical element which may store the IMEI for MS 1002. Userequipment may be classified as either “white listed” or “blacklisted”depending on its status in the network. If MS 1002 is stolen and put touse by an unauthorized user, it may be registered as “blacklisted” inEIR 1044, preventing its use on the network. An MME 1046 is a controlnode which may track MS 1002 or UE 1024 if the devices are idle.Additional functionality may include the ability of MME 1046 to contactidle MS 1002 or UE 1024 if retransmission of a previous session isrequired.

While examples of described telecommunications system have beendescribed in connection with various computing devices/processors, theunderlying concepts may be applied to any computing device, processor,or system capable of facilitating a telecommunications system. Thevarious techniques described herein may be implemented in connectionwith hardware or software or, where appropriate, with a combination ofboth. Thus, the methods and devices may take the form of program code(i.e., instructions) embodied in concrete, tangible, storage mediahaving a concrete, tangible, physical structure. Examples of tangiblestorage media include floppy diskettes, CD-ROMs, DVDs, hard drives, orany other tangible machine-readable storage medium (computer-readablestorage medium). Thus, a computer-readable storage medium is not asignal. A computer-readable storage medium is not a transient signal.Further, a computer-readable storage medium is not a propagating signal.A computer-readable storage medium as described herein is an article ofmanufacture. When the program code is loaded into and executed by amachine, such as a computer, the machine becomes a device fortelecommunications. In the case of program code execution onprogrammable computers, the computing device will generally include aprocessor, a storage medium readable by the processor (includingvolatile or nonvolatile memory or storage elements), at least one inputdevice, and at least one output device. The program(s) can beimplemented in assembly or machine language, if desired. The languagecan be a compiled or interpreted language, and may be combined withhardware implementations.

The methods and devices associated with a telecommunications system asdescribed herein also may be practiced via communications embodied inthe form of program code that is transmitted over some transmissionmedium, such as over electrical wiring or cabling, through fiber optics,or via any other form of transmission, wherein, when the program code isreceived and loaded into and executed by a machine, such as an EPROM, agate array, a programmable logic device (PLD), a client computer, or thelike, the machine becomes an device for implementing telecommunicationsas described herein. When implemented on a general-purpose processor,the program code combines with the processor to provide a unique devicethat operates to invoke the functionality of a telecommunicationssystem.

While a telecommunications system has been described in connection withthe various examples of the various figures, it is to be understood thatother similar implementations may be used, or modifications andadditions may be made to the described examples of a telecommunicationssystem without deviating therefrom. For example, one skilled in the artwill recognize that a telecommunications system as described in theinstant application may apply to any environment, whether wired orwireless, and may be applied to any number of such devices connected viaa communications network and interacting across the network. Therefore,a telecommunications system as described herein should not be limited toany single example, but rather should be construed in breadth and scopein accordance with the appended claims. The term “or” as used herein isinclusive, unless provided otherwise.

The invention claimed is:
 1. A device, the device comprising: aprocessor; and a memory coupled with the processor, the memory storingexecutable instructions that when executed by the processor, cause theprocessor to effectuate operations comprising: receiving a servicecapability for a mobile originating (MO) device; receiving a servicecapability for a mobile terminating (MT) device; receiving sessioninitiation protocol (SIP) messages from the MO device at a BreakoutGateway Control Function (BGCF); determining whether the SIP messagesare associated with setting up an outgoing open group chat (OGC) or anoutgoing Message Session Relay Protocol (MSRP) file transfer; routingthe SIP messages to the MT device in response to the determination thatthe SIP messages are associated with setting up an outgoing OGC andestablishing a rich communication service (RCS) messaging session basedon the service capability of the MO device and the service capability ofthe MT device; and blocking the SIP messages, based on the determiningthat the SIP messages are associated with setting up the MSRP filetransfer.
 2. The device of claim 1, wherein the processor furthereffectuates operations comprising adding or removing participant devicesto the OGC.
 3. The device of claim 2, wherein when adding one or moreparticipant devices to the OGC, each added participant device obtains astatus of each device in the OGC.
 4. The device of claim 1, wherein theprocessor further effectuates operations comprising: receiving, by theBGCF, a SIP INVITE message from the MO device; examining, by the BGCF, aheader of the SIP INVITE message to determine whether the headercontains a predetermined value; and blocking, by the BGCF, the SIPINVITE message from being sent to the MT device when the header of theSIP INVITE message does not contain the predetermined value.
 5. Thedevice of claim 1, wherein the MO device is connected to a first networkand the MT device is connected to a second network.
 6. The device ofclaim 1, wherein the service capability for the MO device and theservice capability of the MT device is received from a user capabilityexchange application server.
 7. The device of claim 1, wherein blockingthe SIP messages associated with setting up the MSRP file transfercomprises filtering MSRP file transfer service tuple in outgoing SIPNOTIFY messages directed to a network associated with the MT device. 8.A computer-implemented method for establishing a messaging sessioncomprising: receiving, by a Breakout Gateway Control Function (BGCF), aservice capability for a mobile originating (MO) device; receiving, bythe BGCF, a service capability for a mobile terminating (MT) device;receiving session initiation protocol (SIP) messages from the MO device;determining, by the BGCF, whether the SIP messages are associated withsetting up an outgoing open group chat (OGC) or an outgoing MessageSession Relay Protocol (MSRP) file transfer; routing, by the BGCF, theSIP messages to the MT device in response to the determination that theSIP messages are associated with setting up an outgoing OGC andestablishing a rich communication service (RCS) messaging session basedon the service capability of the MO device and the service capability ofthe MT device; and blocking, by the BGCF, the SIP messages based on thedetermining that the SIP messages are associated with setting up theMSRP file transfer.
 9. The computer-implemented method of claim 8further comprising adding or removing participant devices to the OGC.10. The computer-implemented method of claim 9, wherein when adding oneor more participant devices to the OGC, each added participant deviceobtains a status of each device in the OGC.
 11. The computer-implementedmethod of claim 8, further comprising: receiving, by the BGCF, a SIPINVITE message from the MO device; examining, by the BGCF, a header ofthe SIP INVITE message to determine whether the header contains apredetermined value; and blocking, by the BGCF, the SIP INVITE messagefrom being sent to the MT device when the header of the SIP INVITEmessage does not contain the predetermined value.
 12. Thecomputer-implemented method of claim 8, wherein the MO device isconnected to a first network and the MT device is connected to a secondnetwork.
 13. The computer-implemented method of claim 8, wherein theservice capability for the MO device and the service capability of theMT device is received from a user capability exchange applicationserver.
 14. The computer-implemented method of claim 8, wherein blockingthe SIP messages associated with setting up the MSRP file transfercomprises filtering MSRP file transfer service tuple in outgoing SIPNOTIFY messages directed to a network associated with the MT.
 15. Acomputer-readable storage medium storing executable instructions thatwhen executed by a computing device cause said computing device toeffectuate operations comprising: receiving a service capability for amobile originating (MO) device; receiving a service capability for amobile terminating (MT) device; receiving session initiation protocol(SIP) messages from the MO device at a Breakout Gateway Control Function(BGCF); determining whether the SIP messages are associated with settingup an outgoing open group chat (OGC) or an outgoing Message SessionRelay Protocol (MSRP) file transfer; routing the SIP messages to the MTdevice in response to the determination that the SIP messages areassociated with setting up an outgoing OGC and establishing a richcommunication service (RCS) messaging session based on the servicecapability of the MO device and the service capability of the MT device;and blocking the SIP messages based on the determining that the SIPmessages are associated with setting up a MSRP file transfer.
 16. Thecomputer-readable storage medium of claim 15, further comprising addingor removing participant devices to the OGC.
 17. The computer-readablestorage medium of claim 16, wherein when adding one or more participantdevices to the OGC, each added participant device obtains a status ofeach device in the OGC.
 18. The computer-readable storage medium ofclaim 15 further comprising: receiving, by the BGCF, a SIP INVITEmessage from the MO device; examining, by the BGCF, a header of the SIPINVITE message to determine whether the header contains a predeterminedvalue; and blocking, by the BGCF, the SIP INVITE message from being sentto the MT device when the header of the SIP INVITE message does notcontain the predetermined value.
 19. The computer-readable storagemedium of claim 15, wherein the MO device is connected to a firstnetwork and the MT device is connected to a second network.
 20. Thecomputer-readable storage medium of claim 15, wherein blocking the SIPmessages associated with setting up the MSRP file transfer comprisesfiltering MSRP file transfer service tuple in outgoing SIP NOTIFYmessages directed to a network associated with the MT device.